Release 10.1A: OpenEdge Getting Started:
Core Business Services

Migrating an existing application to use auditing

The following outline shows what a Progress 4GL developer would do to migrate an existing 4GL application, which did not implement its own auditing service, to use OpenEdge auditing:

Determine whether user-defined application auditing events will be embedded within your application:
Assign an auditing event ID (above 32000) and context string to each auditing event you will embed within your application. You will want to define all of the events that any of the end-customers might want to use. Just because an audit event is embedded within the application does not mean that it needs to be triggered at run time.
Change the Progress 4GL source code to embed the AUDIT-EVENT( ) statements into your application, where appropriate.
Determine whether user-defined application context will be linked to database auditing events:
Choose the location, or locations, in your application where you want to begin linking application context to recorded audit events and optionally when to stop. You do not have to record application context on each recorded audit event.
Embed in the Progress 4GL source code the SET-APPL-CONTEXT( ) method for the AUDIT-CONTROL system handle.
Change your Progress 4GL application’s initialization to set any customized audit-related settings. (Set up the AUDITING-DB alias.)
If user-defined application audit events are embedded in the application, export the database’s application audit event definitions to an intermediate XML file for loading at the installation site.

Once the application is enabled for auditing, the production installation at the end-customer site would follow these steps:

Install OpenEdge Release 10.1A and the 4GL application. If this is an upgrade, ensure that all components are running Release 10.1 or later.
Enable auditing in each of the application’s databases.
Create the user accounts that will be used by auditors and audit administrators in the OpenEdge auditing databases.
Define which user accounts will be given audit administrator privileges.
If the application has incorporated user-defined application audit events, import the user-defined auditing definitions into the databases used to store the application’s auditing configuration.
Configure the database auditing necessary for the end-customer. Using Audit Policy Management or an application-supplied auditing administration utility, configure each database your application uses.
If the application has incorporated user-defined application audit events, configure the application auditing necessary for the end-customer through Audit Policy Maintenance or an application-supplied utility.
Start the application.